Document manual UI testing best practices#5357
Conversation
StephDriver
left a comment
There was a problem hiding this comment.
this looks like a good starting point - and I'm suspecting it is a starting point for this PR (no issue to tell me what the aim is here).
I have added a handful of direct comments. Overall, good - sure, let's start here.
If you are looking to add more now, I think the it might be worth mentioning the build_assets and how to set the domain as those are the two I use most often when UI testing. So easy to forget to build the assets - and so wonder why your change didn't work or to end up with every attempt to reach a page redirecting to example.org if the domain isn't set - especially if you open in a different port to normal to say compare the UI on master alongside your branch.
Please do add things you find helpful once this is merged! I have been approaching these docs-in-progress in a very streamlined manner--only adding sections and pages when they are fresh in my mind because I've just dealt with them while making or fixing something, so I am going to refrain from aiming for completeness at this stage, or I would never emerge from the writing cave 😄 |
No description provided.